Hmm, I don't think it's is a good idea to load stringio module unconditionally. Why doesn't it respond to to_io?

I hope you're just speaking aloud... I have no idea why the implementers of StringIO didn't make it respond to to_io or subclass an IO base class, but it doesn't. Ruby is not my preferred language, but If you don't want to take this contribution my employers will continue using my fork of this repository.

Regarding requiring stringio: I did that because I ruby 1.8.7 does not include it by default and it needs to be required. Although we don't use ruby 1.8.7 I figured you might want not to get bug reports from people using ruby 1.8.7

How about defined?(StringIO) and object.is_a?(StringIO) instead of requiring it?

I guess that's a good alternative. Though I'm not sure it makes much of a
difference. StringIO is a core library it's just not included by default.
On Feb 16, 2013 4:20 PM, "Daiki Ueno" notifications@github.com wrote:

How about defined?(StringIO) and object.is_a?(StringIO) instead of
requiring it?

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/18#issuecomment-13677975.

Does IOCallback works fine with StringIO, which does not provide event triggers?

I've been able to encrypt StringIO files and verify their result. (Single/Multiple recipients + armor)

So as far as I can tell it's working

Fixed in that way: bfede6a